home *** CD-ROM | disk | FTP | other *** search
- ;
- ; Configuration file for Manager, the Multiline BBS, Mailer &
- ; Mail-processor control system written by Koos Kuil on 7 April 1995
- ;
- ; Revision date: 05 Jan 1996 for use with Manager v0.47 Beta
- ;
- ; ** PLEASE READ THIS TEXT VERY CAREFULLY BEFORE YOU DELETE IT **
- ;
- ; THIS CONFIGURATION FILE IS ALSO THE INSTALLATION MANUAL.
- ; """"""""""""""""""""""""""""""""""""""""""""""""""""""""
- ;
- ; SEE textfile UPDATE.MAN for (alpha/beta) update information.
- ;
- ; Hardware requirements: Atari ST with Mag!C, MultiTos or Geneva
- ; and at least 2,5 Mb of internal memory is enough for 2 lines.
- ;
- ; This programm is tested with Mag!C 2.01 and 3.0x, Semper v0.79Beta,
- ; Jetmail v0.99Beta-21 and Octopus v0.68Beta but maybe other programm
- ; versions should work probable too.
- ;
- ; MultiTOS and Geneva are NOT TESTED in practical environment so
- ; i don't give any warranty if it does work or not.
- ;
- ; Remember that Octopus v0.65 and older doesn't have file-locking
- ; capabilities so it's strongly advised to use v0.66 or higher!!!!
- ;
- ; * * * * * * * WARNING * * * * * * *
- ;
- ; You should MAKE a Backup first from your current Octopus and Semper
- ; configuration files before setting up a Multiline board. There's
- ; also absolutely no warranty that it will work without problems.
- ;
- ; Octopus and Semper should be setup using the following style to
- ; work with this manager. For each new line you need an extra folder
- ; and a copy of the existing application.
- ;
- ; For EVERY Octopus you should add "NoBconMap" in the configuration
- ; file and change the modem port (Modem1, Midi, Modem2 etc..) to the
- ; port which should be used for that line.
- ;
- ; Specify also for every Octopus a different logfile and do not forget
- ; to change TRANSFER protocols. XYZ is not usable, i advice to use
- ; the GEM Sz Rz package from Michael Ziegler.
- ;
- ; Take the time for setting up your Multiline bulletin board, most
- ; file-locking functions are ready in Octopus v0.66 so it should all
- ; work correctly.
- ;
- ; LED 1.29 and older does not like if a message area is already used
- ; by another application and will BOMB out. LED 1.30 should work
- ; better but it's UNTESTED.
- ;
- ; External archivers can have problems with memory, i advice to use
- ; the QWK Batch-Pack when you have less memory installed.
- ;
- ; Octopus should be setup as following:
- ;
- ; \OCTOPUS1\
- ; MENUS\
- ; ONLINE\
- ; SYSTEM\ (main SystemPath)
- ; ARCHIVER\
- ; OCTOPUS.CFG (Change this for every line)
- ; OCTOPUS1.APP
- ; OCTOPUS?.RSC
- ;
- ; \OCTOPUS2\
- ; ONLINE\
- ; SYSTEM\ (TaskSystemPath)
- ; ARCHIVER\
- ; OCTOPUS.CFG (Change this for every line)
- ; OCTOPUS2.APP
- ; OCTOPUS?.RSC
- ;
- ; Add "NoBconMap", change every modem port and give every task a
- ; unique logfile (like C:\OCTOPUS1\LOGFILES\OCTOPUS1, OCTOPUS2 etc..)
- ;
- ; A good idea for all OCTOPUS.CFG files is to make one like:
- ;
- ; ; OCTOPUS.CFG
- ; ;
- ; ; Enable Message, Userbase & Miscellaneous filelocking.
- ; ;
- ; FileLocking
- ; ;
- ; ; Second SystemPath for task-dependent files
- ; ;
- ; TaskSystemPath D:\OCTOPUS2\SYSTEM\
- ; Port ...
- ; NoBconMap
- ; Logfilename D:\OCTOPUS1\OCTOPUS1.LOG
- ; ;
- ; Include D:\OCTOPUS1\OCTOPUS.CFG
- ; ;
- ; ; End OCTOPUS.CFG
- ;
- ; Using this way you don't need to make changes in all Octopus
- ; configuration files if you add or remove message/file areas.
- ;
- ; Above commands should be removed from the ORIGINAL OCTOPUS.CFG
- ; file otherwise it doesn't work.
- ;
- ; Do also SHARE the FILE and MESSAGE areas by using a include file
- ; so that you don't get 2 setups with different number of areas
- ; what will result in heavy MAF calls.
- ;
- ; ; OCTOPUS.CFG
- ; ;
- ; Include FILEAREA.CFG
- ; Include MSGAREA.CFG
- ; ;
- ; ...
- ;
- ; For Semper it's simulair but a bit different and needs more tricks
- ; to let it work correctly. Do also specify for every new Semper a
- ; new logfile like done by Octopus (or use the same one as used by
- ; the same Octopus task)
- ;
- ; \SEMPER1\
- ; SEMPER\
- ; CONFIG.SYS (Change for every Semper the port)
- ; SEMPER.APP
- ; SMP_HIGH.RSC
- ;
- ; \SEMPER2\
- ; SEMPER\
- ; CONFIG.SYS (Change for every Semper the port)
- ; SEMPER.APP
- ; SMP_HIGH.RSC
- ;
- ; Startup manually each Semper to give them the right modem port as
- ; used by Octopus. Do not run 2 Semper's together before this is
- ; changed because it's not possible to initialize the same modem ports.
- ;
- ; Some EXECUTABLES should be changed to the following:
- ;
- ; Import : SENDMSG.APP
- ; cmd: Manager Import
- ;
- ; Export : SENDMSG.APP
- ; cmd: Manager Export
- ;
- ; Scan : SENDMSG.APP
- ; cmd: Manager Scan
- ;
- ; Maint : SENDMSG.APP
- ; cmd: Manager Maint
- ;
- ;
- ; The included programm SENDMSG.APP is a small utility which says
- ; to the Manager that Semper does want "Import" or "Export" or
- ; something else. Mail-Processor (Like Jetmail) can't be started
- ; when a user is online and the Manager will wait until both lines
- ; are free, terminate Semper and then doing the job he should do.
- ;
- ; The Terminal, MSG-Editor and Text-Editor can be cleared because
- ; they will not be used.
- ;
- ; In the OTHER Config from Semper (Miscellaneous settings) should
- ; the BBS programm startup changed a bit.
- ;
- ; Type: * Function
- ;
- ; Aftermail : SENDMSG.APP Manager Function1
- ; or: SEMDMSG.APP Manager Import
- ;
- ; NOTE: Function 1 should be defined as Import event when you call
- ; a function.
- ;
- ; ALL Functions defined in Semper should be configured in the Manager
- ; configuration file using Function <nr> {} options. To save memory
- ; (at least 400 Kb) the manager will control them now.
- ;
- ; The BBS should be started with "EXIT", it can't be started using
- ; Function or ShellScript because Semper will be terminated during the
- ; BBS session.
- ;
- ; If you already have configured a function or a name/path, remove
- ; it because we don't need that.
- ;
- ; The FAX receiver is not tested, i think that it uses the wrong
- ; modem port but i'm not sure about it because it's untested. A new
- ; update should be necessary with a option line -p <port number>
- ; """"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
- ;
- ; The name of the logfile should have a full pathname
- ; and not only a filename.
- ;
- LogfileName F:\MANAGER\MANAGER.LOG
- ;
- ; Standard Executables as defined in SEMPER (change them to your
- ; own settings), an optional value can be added to indicate that
- ; it can be started via an Error-Level (such as used by Binkley)
- ;
- ; Like: Import F:\JETMAIL.TTP 10 (Mailer-Exit errorlevel 10
- ; does also run Import)
- ;
- Import F:\JETMAIL.TTP
- ImportCMD import pack bundle
- ;
- Export F:\JETMAIL.TTP
- ExportCMD pack bundle
- ;
- Scanner F:\JETMAIL.TTP
- ScannerCMD scan bundle
- ;
- Maintain F:\JETMAIL.TTP
- MaintainCMD maint
- ;
- Ticker F:\JETMAIL.TTP
- TickerCMD tick
- ;
- Reader F:\BINKLEY\LED.PRG
- Editor C:\PC\PC.PRG
- ;
- ; Octopus must know where he can find MAF because it's used when
- ; a user wants to download a QWK mail packet. After a request from
- ; the users side MAF will be started immediately after logoff to
- ; get the packet ready to download for the user.
- ;
- Maf C:\OCTOPUS1\MAF.TTP
- ;
- ; Errorlevels they indicate us to start the BBS (Binkley and Semper
- ; both does support these, when not you can simply add them).
- ;
- ; ALL Semper versions below v0.79 does contain a bug in the Exit
- ; mode, the errorlevel of the current connection is NOT returned!
- ; It does return 0 in case of 24 for 2400 baud.
- ;
- ; Semper v0.79 does finally give the correct errorlevels back
- ; so we can later make use of it. It's on this moment RESERVED
- ; so you don't have to change this.
- ;
- BBS_ErrLevels 3 12 24 48 72 96 120 144 168 192 216 240 264 288
- ;
- ; Current Semper versions does not support a Quit option using
- ; GEM message handling functions. To get the same effect a GEM
- ; message is send with a menu bar action (quit is selected). When
- ; a Jan does make many changes in his resource file it can be needed
- ; to change the next values.
- ;
- QuitObject 24
- ;
- ; The MailerTimeout value does set the Mailer quit timeout in
- ; seconds until the Manager does stop with trying to terminate
- ; them and restart the already terminated mailers again.
- ;
- ; Do not use values below 10 seconds unless you have a very
- ; fast modem initialize. Default value is 30 seconds.
- ;
- ; Use HIGH values (like 3600) if the Manager should wait very
- ; long before he can terminate a mailer (the Mailer can be busy
- ; with a session).
- ;
- ; MailerTimeout 60
- ;
- ; Mailer Executables, the number is currently limited to 20
- ;
- ; Explanation:
- ;
- ; Executables
- ; {
- ; <Start-Id> <type> <Drive:Path\Filename> ["<cmdline>"] <Next-Programm>
- ; ...
- ; }
- ;
- ; Start-Id can be one of: EXEC-1 to EXEC-99 which is used to
- ; indicate a unique number for every programm.
- ;
- ; Type indicates the programm type which can be:
- ;
- ; DIRECT The programm will be STARTED only when the Manager
- ; is executed, the MAILER's are started later.
- ;
- ; MAILER This type indicated that the programm is a MAILER
- ; and will be started after programms with type DIRECT
- ;
- ; BBS Indicates that the programm is a BBS (Octopus ofcourse).
- ; OTHER Unknown programm type, if you want to run other programms
- ; after the BBS session you can use this type.
- ;
- ; Drive:Path\Filename is used to specify the place of every
- ; programm (like the BBS and Mailer)
- ;
- ; Next-Programm is very important and tells the Manager what
- ; programm should be started after it.
- ;
- Executables
- {
- EXEC-1 MAILER F:\SEMPER1\SEMPER.APP EXEC-3
- EXEC-2 MAILER F:\SEMPER2\SEMPER.APP EXEC-4
- EXEC-3 BBS C:\OCTOPUS1\OCTOPUS1.APP "Mailer" EXEC-1
- EXEC-4 BBS C:\OCTOPUS2\OCTOPUS2.APP "Mailer" EXEC-2
- }
- ;
- ; To avoid memory problems all functions are not longer controlled
- ; by Semper but everything is done now by the Manager.
- ;
- ; Maximum 100 functions are definable, everyone with a different
- ; number (like in Semper), the number of actions/function is
- ; not limited, you can also use NESTED functions (as done in Semper).
- ;
- ; REMOVE all your configured functions in Semper and replace them
- ; all only by:
- ;
- ; Type: * Programm
- ;
- ; Path/Name : SENDMSG.APP
- ; cmd : Manager Function-1 (... to Function-40)
- ;
- ; Using this way all events can be used as normally and actions
- ; which are needed to be done are controlled by the Manager.
- ;
- ; When more commandline arguments are used then one it's required
- ; to place then between " " chars (like in Octopus).
- ;
- ; Function <number> ["<description>"]
- ; {
- ; <Drive:Path\Filename> <Commandline>
- ; ...
- ; }
- ;
- Function 1 "Local login"
- {
- D:\OCTOPUS1\OCTOPUS1.APP Local
- }
- ;
- Function 2 "Import"
- {
- F:\JETMAIL.TTP "Import Pack Bundle"
- D:\OCTOPUS\MAF.TTP "ScanMail"
- }
- ;
- Function 3 "Export"
- {
- F:\JETMAIL.TTP "Scan Pack Bundle"
- D:\OCTOPUS\MAF.TTP
- }
- ;
- Function 4 "Maintain"
- {
- D:\OCTOPUS\MAF.TTP ScanMail
- F:\JETMAIL.TTP Maint
- D:\OCTOPUS\MAF.TTP FixLastread
- F:\SEMPER\REQUESTC.TOS
- }
- ;
- ; And so on... with your own functions... Enjoy the installation!
- ;
- ; End MANAGER.CFG
- ;